chore: release package (rc) - #2860
Merged
Merged
Conversation
|
Ladon does not review bot-authored PRs. |
aao-ipr-bot
Bot
force-pushed
the
changeset-release/main
branch
from
September 8, 2026 11:33
bb21c8e to
ab1dd3e
Compare
bokelley
approved these changes
Sep 8, 2026
bokelley
left a comment
bokelley
left a comment
Contributor
There was a problem hiding this comment.
Reviewed generated RC release diff; version, changelog, package metadata, and generated documentation stamps are consistent. All required checks pass.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@adcp/sdk@14.0.0-rc.34
Minor Changes
a8960a5: Expose the AdCP 3.2
error.buyer_reasonsub-object on the client-facing error surfaces.AdcpErrorInfo.buyer_reasonandExtractedAdcpError.buyer_reasonnow carry the buyer-safe{ code, message }when the producer populated it.buildExtracted,extractAdcpErrorInfo, andextractAdcpErrorFromMcp/extractAdcpErrorFromTransportall forward it; partial payloads (missingcodeormessage, empty strings, non-object values) are dropped rather than surfaced as half-typed values a caller might render to a buyer.AdcpStructuredError.buyer_reasonandAdcpErrorconstructor option added so seller-side adopters can throw a coarse top-level code with a specific buyer-actionable classification.adcpError()(viaAdcpErrorOptions) now accepts and emitsbuyer_reason; the framework's sync-throw projection (projectThrownAdcpError) and the two-layer error dispatcher (sanitizePayloadError,PAYLOAD_ERROR_FIELDS) both carry the field through to the wire.BuyerRetryPolicyoverrides receive the field on theerrorargument and can key retry decisions onerror.buyer_reason?.code; the default policy is unchanged — routing onbuyer_reasonis opt-in via override.NormalizedErrorandnormalizeError()(@adcp/sdk/server) now carrybuyer_reasontoo, so adopters projecting per-row batch errors throughnormalizeErrors()(sync_creatives,sync_audiences,sync_accounts,report_usage,acquire_rights) don't silently lose the field between their row objects and the wire.IDEMPOTENCY_CONFLICT/IDEMPOTENCY_IN_FLIGHTenvelope allowlists still stripbuyer_reason— those wire-shape-restricted codes intentionally never carry a buyer-actionable classification.15c8ee8: Add Public Suffix List-backed BrandRef domain validation with explicit, narrow development-domain exceptions.